Skip to content

feat: [DTOSS-12217] allow a newer azurerm provider version than 4.34.0 in container app module#278

Merged
MacMur85 merged 1 commit intomainfrom
feat/DTOSS-12217-update-azurerm-version-templates
Feb 18, 2026
Merged

feat: [DTOSS-12217] allow a newer azurerm provider version than 4.34.0 in container app module#278
MacMur85 merged 1 commit intomainfrom
feat/DTOSS-12217-update-azurerm-version-templates

Conversation

@MacMur85
Copy link
Contributor

@MacMur85 MacMur85 commented Feb 17, 2026

Description

This PR is a part of the regular AzureRM Terraform provider update cycle.
This PR needs to be merged before the CohMan repository PR.

Context

Previously the AzureRM provider version in Templates container-app module was set to a "4.34.0".
In order to be able to better manage the provider version used in the client repositories, we won't be pinning a specific provider version anymore.

Rather than pointing to a single version, we will allow using the previously pinned "4.34.0" or newer, as defined in the client repository.

New version definition is ">= 4.34.0"

More on the provider version constraints in terraform modules can be found here.

Successful deployment plan (no changes) using this branch in CohMan Sandbox Audit:
image

Successful deployment apply using this branch in CohMan Sandbox Core:
https://dev.azure.com/nhse-dtos/dtos-cohort-manager/_build/results?buildId=33890&view=logs&j=2e61fdd4-29ab-51b4-3516-655c0df6fcf2&t=430e7011-249c-5e1a-31f4-0c3babbc029d

Type of changes

  • Refactoring (non-breaking change)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would change existing functionality)
  • Bug fix (non-breaking change which fixes an issue)

Checklist

  • I am familiar with the contributing guidelines
  • I have followed the code style of the project
  • I have added tests to cover my changes
  • I have updated the documentation accordingly
  • This PR is a result of pair or mob programming

Sensitive Information Declaration

To ensure the utmost confidentiality and protect your and others privacy, we kindly ask you to NOT including PII (Personal Identifiable Information) / PID (Personal Identifiable Data) or any other sensitive data in this PR (Pull Request) and the codebase changes. We will remove any PR that do contain any sensitive information. We really appreciate your cooperation in this matter.

  • I confirm that neither PII/PID nor sensitive data are included in this PR and the codebase changes.

@MacMur85 MacMur85 force-pushed the feat/DTOSS-12217-update-azurerm-version-templates branch from cdb3070 to df8133d Compare February 17, 2026 20:42
@MacMur85 MacMur85 changed the title Feat [DTOSS-12217] update azurerm version templates feat: [DTOSS-12217] update azurerm version templates Feb 17, 2026
@MacMur85 MacMur85 changed the title feat: [DTOSS-12217] update azurerm version templates feat: [DTOSS-12217] update the azurerm provider to 4.59.0 Feb 17, 2026
@MacMur85 MacMur85 marked this pull request as ready for review February 18, 2026 10:06
@MacMur85 MacMur85 changed the title feat: [DTOSS-12217] update the azurerm provider to 4.59.0 feat: [DTOSS-12217] allow use a newer azurerm provider version than 4.34.0 in container app module Feb 18, 2026
@MacMur85 MacMur85 changed the title feat: [DTOSS-12217] allow use a newer azurerm provider version than 4.34.0 in container app module feat: [DTOSS-12217] allow a newer azurerm provider version than 4.34.0 in container app module Feb 18, 2026
…than 4.34.0

docs: update the readme file with provider management section
@MacMur85 MacMur85 force-pushed the feat/DTOSS-12217-update-azurerm-version-templates branch from 522d163 to 4613d30 Compare February 18, 2026 13:41
@MacMur85 MacMur85 added this pull request to the merge queue Feb 18, 2026
Merged via the queue into main with commit ede5951 Feb 18, 2026
13 checks passed
@MacMur85 MacMur85 deleted the feat/DTOSS-12217-update-azurerm-version-templates branch February 18, 2026 16:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants

Comments